Skip to content

feat: add scheduled merge workflow for blog PRs#35

Merged
ajbozarth merged 1 commit intogenerative-computing:mainfrom
ajbozarth:feat/scheduled-merge
May 4, 2026
Merged

feat: add scheduled merge workflow for blog PRs#35
ajbozarth merged 1 commit intogenerative-computing:mainfrom
ajbozarth:feat/scheduled-merge

Conversation

@ajbozarth
Copy link
Copy Markdown
Contributor

Summary

Adds a GitHub Actions workflow that automatically merges PRs on a scheduled date by enabling auto-merge and routing through the existing merge queue.

  • New workflow: .github/workflows/merge-schedule.yml
  • Documentation added to AGENTS.md and CONTRIBUTING.md

How to use

Add this line anywhere in the PR description:

/schedule 2026-05-15

The workflow runs daily at ~9am Eastern. When the date arrives and the PR is already approved, it enables auto-merge — the PR then goes through the normal merge queue like any other. If the PR is not yet approved, it posts a warning comment on the PR.

Design notes

  • Uses GITHUB_TOKEN (no PAT or GitHub App needed) — sufficient for enabling auto-merge on an already-approved PR
  • Does not bypass branch protection or the merge queue; the scheduled action only calls gh pr merge --auto
  • Scheduling is opt-in: the /schedule line is not required and should only be added when a future publish date is intended
  • Merge method is squash; adjust in the workflow if needed

@ajbozarth ajbozarth self-assigned this May 4, 2026
Signed-off-by: Alex Bozarth <ajbozart@us.ibm.com>
@ajbozarth ajbozarth force-pushed the feat/scheduled-merge branch from de8aa36 to 3aa3ef8 Compare May 4, 2026 17:18
@ajbozarth ajbozarth marked this pull request as ready for review May 4, 2026 17:20
@ajbozarth ajbozarth requested a review from a team as a code owner May 4, 2026 17:20
@ajbozarth ajbozarth requested review from jakelorocco and nrfulton May 4, 2026 17:20
Copy link
Copy Markdown
Member

@psschwei psschwei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to run the job to build the site after this runs? I'm not 100%, but if so I don't believe this will trigger that job (because it's using the GITHUB_TOKEN, and that mostly doesn't run additional workflows)

@ajbozarth
Copy link
Copy Markdown
Contributor Author

Do we need to run the job to build the site after this runs

No, this is one of the reasons I actually wrote it myself instead of using an existing action. this action actually just adds the pr to the merge queue using the gh cli and does not try to merge it itself. That allow us to continue to use our current process as is.

Copy link
Copy Markdown
Member

@psschwei psschwei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's try it

@ajbozarth ajbozarth added this pull request to the merge queue May 4, 2026
Merged via the queue into generative-computing:main with commit c461a34 May 4, 2026
6 checks passed
@ajbozarth ajbozarth deleted the feat/scheduled-merge branch May 4, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants